I have a script that opens 2 baselines of a particular module and shows the deletions in each. However, there are certain times in the script where I'd like to hide the deletions before performing an action. Can this be done? The times I need to hide deletions is when I am working with headings in the module. When I get to a heading that has changed, I want to hide any hidden sections above it so that it will display the correct number.
Chris chrscote - Tue Feb 14 15:05:20 EST 2017 |
Re: Hide/show deleted objects get: bool deletions (Module) set: void deletions (bool) toggle: deletions(!deletions(current Module))
|
Re: Hide/show deleted objects OK, I understand the concept of using the deletions function, but what if you have 2 baselines of the same module open? Do I have to perform the toggle on both baselines, or does this function automatically set it for all open baselines? |
Re: Hide/show deleted objects chrscote - Wed Feb 15 08:22:57 EST 2017 OK, I understand the concept of using the deletions function, but what if you have 2 baselines of the same module open? Do I have to perform the toggle on both baselines, or does this function automatically set it for all open baselines? I would say that "deletions" works on the current Module. so, if you have variables modBL1 and modBL2 of type Module, you can say current = modBL1 deletions(true) By the way, I played around a bit with this now and it seems that you have to add two more statements to refresh the view: refresh modBL1 synchExplorer modBL1 If you want to change the setting for every open module, you could use something like
Module m
for m in database do {
current = m
deletions (true)
refresh m
synchExplorer(m)
}
|
Re: Hide/show deleted objects Mike.Scharnow - Wed Feb 15 08:46:01 EST 2017 I would say that "deletions" works on the current Module. so, if you have variables modBL1 and modBL2 of type Module, you can say current = modBL1 deletions(true) By the way, I played around a bit with this now and it seems that you have to add two more statements to refresh the view: refresh modBL1 synchExplorer modBL1 If you want to change the setting for every open module, you could use something like
Module m
for m in database do {
current = m
deletions (true)
refresh m
synchExplorer(m)
}
HOORAY! It works great! However, since I don't actually display the explorer while my script is running, I didn't have to use the last 2 lines. I just added the deletions(true) - deletions(false) around each procedure that writes out a header object. Thank you Mike. |